View BU-61570_5235188.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

bu-65170/61580 and bu-61585 description ddc's bu-65170, bu-61580 and bu-61585 bus controller / remote terminal / monitor terminal (bc/rt/mt) a d v anced communication engine (ace) termi- nals comprise a complete integrated interface between a host processor and a mil-std-1553 a and b or stanag 3838 bus. the ace series is packaged in a 1.9 - square-inch, 70-pin, low-profile, cofired multichip module (mcm) ceramic package that is well suited for applications with stringent height requirements. the bu-61585 ace integrates dual transceiver, protocol, memory man- agement, processor interface logic, and a total of 12k words of ram in a choice of dip or flat pack packages. the bu-61585 requires +5 v power and either -15 v or -12 v power. the bu-61585 internal ram can be configured as 12k x 16 or 8k x 17. the 8k x 17 ram feature provides capability for memory integrity check- ing by implementing ram parity gen- eration and verification on all access- es. to minimize board space and ?glue? logic, the ace provides ultimate flexibility in interfacing to a host processor and internal/external ram. the advanced functional architecture of the ace terminals provides soft- ware compatibility to ddc's advanced integrated multiplexer (aim) series hybrids, while incorporating a multiplicity of architectural enhance- ments. it allows flexible operation while off-loading the host processor, ensuring data sample consistency, and supports bulk data transfers. the ace hybrids may be operated at either 12 or 16 mhz. wire bond options allow for programmable rt address (hardwired is standard) and external transmitter inhibit inputs. mil-std-1553a/b notice 2 rt and bc/rt/mt, advanced communication engine (ace) features fully integrated mil-std-1553 interface terminal flexible processor/memory interface standard 4k x 16 ram and optional 12k x 16 or 8k x 17 ram available optional ram parity generation/checking automatic bc retries programmable bc gap times bc frame auto-repeat flexible rt data buffering programmable illegalization selective message monitor simultaneous rt/monitor mode transceiver a ch. a transceiver b ch. b dual encoder/decoder, multiprotocol and memory management rt address shared ram address bus processor and memory interface logic data bus d15-d0 a15-a0 data buffers address buffers processor data bus processor address bus miscellaneous incmd clk_in, tag_clk, mstclr,ssflag/ext_trg rtad4-rtad0, rtadp transparent/buffered, strbd, select, rd/wr, mem/reg, trigger_sel/memena-in, msb/lsb/dtgrt ioen, memena-out, readyd addr_lat/memoe, zero_wait/memwr, 8/16-bit/dtreq, polarity_sel/dtack int processor and memory control interrupt request tx/rx_a tx/rx_a tx/rx_b tx/rx_b * * see ordering information for available memory ? 1992, 1999 data device corporation ace user?s guide also available figure 1. ace block diagram http://www..net/ datasheet pdf - http://www..net/
2 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 table 1. ?ace? series specifications parameter min typ max units absolute maximum rating supply voltage ! logic +5v ! transceiver +5v ! -15v ! -12v logic ! voltage input range -0.3 -0.3 -18.0 -18.0 -0.3 7.0 7.0 0.3 0.3 v cc +0.3 v v v v v receiver differential input resistance ! (bu-65170/61580/61585x1, bu-65170/61580/61585x2) (notes 1-7) ! (bu-65170/61580/61585x3, bu-65170/61580/61585x6) (notes 1-7) differential input capacitance ! (bu-65170/61580/61585x1, bu-65170/61580/61585x2) (notes 1-7) ! (bu-65170/61580/61585x3, bu-65170/61580/61585x6) (notes 1-7) threshold voltage, transformer coupled, measured on stub common mode voltage (note 7) 11 2.5 0.200 10 5 0.860 10 k ? ? logic v ih v il i ih (vcc=5.5v, v in =vcc) i ih (vcc=5.5v, v in =2.7v) ! ssfla g /ext_trig ! all other inputs i il (vcc=5.5v, v in =0.4v) ! ssfla g /ext_trig ! all other inputs v oh (vcc=4.5v, v ih =2.7v, v il =0.2v, i oh =max) v ol (vcc=4.5v, v ih =2.7v, v il =0.2v, i ol =max) i ol ! db15-db0, a15-a0, memoe / addr_lat, memwr / zer o w ait , dtreq /16/8 , dt a ck /polarity_sel 2.0 -10 -692 -346 -794 -397 2.4 6.4 0.8 10 -84 -42 -100 -50 0.4 v v power supply requirements voltages/tolerances ! bu-65170/61580/61585x1 +5v (logic) +5v (ch. a, ch. b) -15v (ch. a, ch. b) ! bu-65170/61580/61585x2 +5v (logic) +5v (ch. a, ch. b) -12v (ch. a, ch. b) ! bu-65170/61580/61585x3, bu-65170/61580/61585x6 +5v (logic) +5v (ch. a, ch. b) current drain (total hybrid) ! bu-65170/61580x1 +5v (logic, ch. a, ch. b) -15v (ch. a, ch. b) idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-65170/61580x2 +5v (logic, ch. a, ch. b) -12v (ch. a, ch. b) idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-65170/61580x3, bu-65170/61580x6 +5v (logic, ch. a, ch. b) idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-61585x1 +5v (logic, ch. a, ch. b) -15v (ch. a, ch. b) idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ma ma ma pf pf -6.4 -3.2 50 50 3.2 units max typ min parameter table 1. ?ace? series specifications (contd) transmitter differential output voltage ! direct coupled across 35 ? ! transformer coupled across 70 ? (bu-65170/61580/61585x1) (bu-65170/61580/61585x2,x3, x6) output noise, differential (direct coupled) output offset voltage, transformer coupled across 70 ohms rise/fall time logic (cont?d) ! incmd , int memena_out , read yd , ioen , txa, txa , txb, txb , tx_inh_out_a , tx_inh_out_b , i oh ! db15-db0, a15-a0, memoe / addr_lat, memwr / zer o w ait , dtreq /16/8 , dt a ck /polarity_sel ! incmd , int , memena_out , read yd , ioen , txa, txa , txb, txb , tx_inh_out_a , tx_inh_out_b, c i (input capacitance) c io (bi-directional signal input capacitance) 5.0 5.0 -15.0 5.0 5.0 -12.0 5.0 5.0 95 30 68 105 180 95 30 80 130 230 95 245 360 590 105 30 68 105 180 http://www..net/ datasheet pdf - http://www..net/
3 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 ma ma ma ma ma ma ma ma ma w w w w w w w w w w w w w w w w w w w w w w w w w w w w w w w w w w w w 240 60 120 185 305 250 400 550 850 1.85 2.25 2.72 3.52 1.67 2.10 2.59 3.46 1.00 1.43 1.86 2.72 2.10 2.50 2.97 3.77 1.92 2.35 2.84 3.71 1.25 1.68 2.11 2.97 0.68 1.06 1.45 2.23 0.59 0.92 1.36 2.16 0.25 0.68 1.11 1.97 105 30 80 130 230 105 255 370 600 ! bu-61585x2 +5v (logic, ch. a, ch. b) -12v (ch. a, ch. b) idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-61585x3, bu-61585x6 +5v (logic, ch. a, ch. b) idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle power dissipation total hybrid ! bu-65170/61580x1 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-65170/61580x2 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-65170/61580x3, bu-65170/61580x6 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-61585x1 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-61585x2 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-61585x3, bu-61585x6 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle hottest die ! bu-65170/61580x1 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-65170/61580x2 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-65170/61580x3, bu-65170/61580x6 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle units max typ min parameter table 1. ?ace? series specifications (contd) oz (g) 0.6 (17) in. (mm) in. (mm) w w w w w w w w w w w w 1.9 x 1.0 x 0.165 (48.3 x 25.4 x 4.19) 1.9 x 1.0 x 0.150 (48.3 x 25.4 x 3.81) physical characteristics size ! bu-65170/61580/61585 s ! bu-65170/61580/61585 v weight ! bu-65170/61580/61585 s/v c/w c/w c c c 6.99 6.8 150 150 +300 -55 -65 thermal thermal resistance, junction-to-case, hottest die ( ! bu-65170/61580/61585x1, bu-65170/61580/61585x2, ! bu-65170/61580/61585x3, bu-65170/61580/61585x6 operating junction temperature storage temperature lead temperature (soldering, 10 sec.) mhz mhz % % % % % % clock input frequency ! nominal value (programmable) default mode software programmable option ! long term tolerance 1553a mode 1553b mode ! short term tolerance, 1 second 1553a mode 1553b mode ! duty cycle 16 mhz 12 mhz 1553 message timing completion of cpu write (bc start)- to-start of next message bc intermessage gap (note 8) bc/rt/mt response timeout (note 9) ! 18.5 nominal ! 22.5 nominal ! 50.5 nominal ! 128.0 nominal rt response timeout (note 11) transmitter watchdog timeout units max typ min parameter 0.68 1.06 1.45 2.23 0.59 0.92 1.36 2.16 0.25 0.68 1.11 1.97 0.335 0.600 0.860 1.385 0.290 0.590 0.890 1.490 0.200 0.630 0.885 1.395 ! bu-61585x1 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-61585x2 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle ! bu-61585x3, bu-61585x6 idle 25% transmitter duty cycle 50% transmitter duty cycle 100% transmitter duty cycle table 1. ?ace? series specifications (contd) 0.850 1.195 1.450 1.975 0.835 1.135 1.435 2.035 0.475 0.905 1.160 1.670 0.900 1.245 1.500 2.025 0.885 1.185 1.485 2.085 0.525 0.955 1.210 1.720 0.335 0.600 0.860 1.385 0.290 0.590 0.890 1.490 0.200 0.630 0.885 1.395 http://www..net/ datasheet pdf - http://www..net/
4 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 introduction ddc's ace series of integrated bc/rt/mt hybrids provide a complete, flexible interface between a microprocessor and a mil-std-1553a, b notice 2, mcair, or stanag 3838 bus, implementing bus controller, remote terminal (rt) and monitor terminal (mt) modes. packaged in a single 1.9-square-inch, 70-pin dip or surface mountable flatpack or j-lead package, the ace series contains dual low-power transceivers and encoder/decoders, complete bc/rt/mt multi-protocol logic, memory management and interrupt logic, 4k x 16 of shared sta- tic ram and a direct, buffered interface to a host processor bus. the bu-65170/61580 contains internal address latches and bidi- rectional data buffers to provide a direct interface to a host processor bus. the bu-65170/61580 may be interfaced directly to both 16-bit and 8-bit microprocessors in a buffered shared ram configuration. in addition, the ace may connect to a 16-bit processor bus via a direct memory access (dma) interface. the bu-65170/61580 includes 4k words of buffered ram. alternatively, the ace may be interfaced to as much as 64k words of external ram in either the shared ram or dma config- urations. the ace rt mode is multiprotocol, supporting mil-std-1553a, mil-std-1553b notice 2, stanag 3838 (including efabus), and the mcair a3818, a5232, and a5690 protocols. full compli- ance to the mcair specs, however, requires the use of a sinu- soidal transceiver (transceiver option 5). refer to the bu-61590 data sheet for additional information on mcair terminals. the memory management scheme for rt mode provides an option for separation of broadcast data, in compliance with 1553b notice 2. both double buffer and circular buffer options are programmable by subaddress. these features serve to ensure data consistency and to off-load the host processor for bulk data transfer applications. the ace series implements three monitor modes: a word moni- tor, a selective message monitor, and a combined rt/selective monitor. other features include options for automatic retries and programmable intermessage gap for bc mode, an internal time tag register, an interrupt status register and internal command illegalization for rt mode. functional overview transceivers the transceivers in the bu-65170/61580x3(x6) are fully mono- lithic, requiring only a +5 volt power input. besides eliminating the need for an additional power supply, the use of a 5 volt (only) transceiver requires the use of step-up, rather than step-down, isolation transformers. this provides the advantage of a higher terminal input impedance than is possible for a 15 volt or 12 volt transmitter. as a result, there is greater margin for the input impedance test, mandated for 1553 validation testing. this allows for longer cable lengths between an lru's system con- nector and the isolation transformers of an embedded 1553 ter- minal. for the +5 v and -15 v/-12 v front end, the bu-65170/ 61580x1(x2) uses low-power bipolar analog monolithic and thick-film hybrid technology. the transceiver requires +5 v and - 15 v (-12 v) only (requiring no +15 v/+12 v) and includes volt- age source transmitters. the voltage source transmitters provide superior line driving capability for long cables and heavy amounts of bus loading. in addition, the monolithic transceivers in the bu-65170/61580x1 provide a minimum stub voltage level of 20 volts peak-to-peak transformer coupled, making them suit- able for mil-std-1760 applications. the receiver sections of the bu-65170/61580 are fully compliant with mil-std-1553b in terms of front end overvoltage protec- tion, threshold, common mode rejection, and word error rate. in addition, the receiver filters have been designed for optimal oper- ation with the j chip's manchester ii decoders. j digital monolithic the j digital monolithic represents the cornerstone element of the ace family of terminals. the development of the j chip rep- resents the fifth generation of 1553 protocol and interface design for ddc. over the years, ddc's 1553 protocol and interface design has evolved from: (1) discrete component sets, consisting of multiple hybrids (with large numbers of chips inside the indi- vidual hybrids) and programmable logic devices, to (2) multiple custom asics to perform the functions of encoder/decoder and rt protocol within a single hybrid, to (3) the bus-61553 advanced integrated mux hybrid (aim-hy) series, containing, in addition to a dual monolithic/thick-film transceiver and discrete ram chips, a custom protocol chip and a separate custom mem- ory management/processor interface chip, to (4) the bus-61559 advanced integrated mux hybrids with enhanced rt features (aim-hy'er ? the aim-hy'er series includes memory manage- ment and processor interface functions beyond those of the aim- hy series) , to (5) the full integration of the j chip. notes for table 1: notes 1 through 6 are applicable to the receiver differential resistance and differential capacitance specifications: (1) specifications include both transmitter and receiver (tied together internally). (2) measurement of impedance is directly between pins tx/rx a(b) and tx/rx a(b) of the bu-65170/61580xx hybrid. (3) assuming the connection of all power and ground inputs to the hybrid. (4) the specifications are applicable for both unpowered and powered conditions. (5) the specifications assume a 2 volt rms balanced, differential, sinu- soidal input. the applicable frequency range is 75 khz to 1 mhz. (6) minimum resistance and maximum capacitance parameters are guaranteed,but not tested, over the operating range. (7) assumes a common mode voltage within the frequency range of dc to 2mhz, applied to pins of the isolation transformer on the stub side (either direct or transformer coupled), referenced to hybrid ground. use a ddc recommended transformer or other transformer that provides an equivalent minimum cmrr. (8) typical value for minimum intermessage gap time. under software control, may be lengthened to (65,535s minus message time), in increments of 1s. (9) software programmable (4 options). includes rt-to-rt timeout (mid-parity of transmit command to mid-sync of transmitting rt status). (10) for both +5v logic and transceiver. +5v for channels a and b. (11) measured from mid-parity crossing of command word to mid-sync crossing of rt's status word. (12) specifications for bu-65171, bu-61581, and bu-61586 are identi- cal to the specifications for the bu-65170, bu-61580, and bu- 61585 respectively. http://www..net/ datasheet pdf - http://www..net/
5 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 the j chip consists of a dual encoder/decoder, complete proto- col for bus controller (bc), 1553a/b/mcair remote terminal (rt), and monitor (mt) modes; memory management and inter- rupt logic; a flexible, buffered interface to a host processor bus and optional external ram; and 4k words of on-chip ram. reference the region within the dotted line of figure 1. besides realizing all the protocol, memory management, and interface functions of the earlier aim-hy'er series, the j chip includes a large number of enhancements to facilitate hardware and soft- ware design, and to further off-load the 1553 terminal's host processor. decoders the default mode of operation for the bu-65170 rt and bu- 61580 bc/rt/mt requires a 16 mhz clock input. if needed, a software programmable option allows the device to be operated from a 12 mhz clock input. most current 1553 decoders sample using a 10 mhz or 12 mhz clock. in the 16 mhz mode (default following a hardware or software reset), the ace decoders sam- ple 1553 serial data using the 16 mhz clock. in the 12 mhz mode, the decoders sample using both clock edges; this pro- vides a sampling rate of 24 mhz. the faster sampling rate for the j chip ? s manchester ii decoders provides superior performance in terms of bit error rate and zero-crossing distortion tolerance. for interfacing to fiber optic transceivers for mil-std-1773 appli- cations, a transceiverless version of the j chip, the bu-65620, can be used. these versions provide a pin-programmable option for a direct interface to the single-ended outputs of a fiber optic receiver. no external logic is needed. time tagging the ace includes an internal read/writable time tag register. this register is a cpu read/writable 16-bit counter with a pro- grammable resolution of either 2, 4, 8, 16, 32, or 64 ? time tag word ? ) for both bc and rt modes. additional provided options will: clear the time tag register fol- lowing a synchronize (without data) mode command or load the time tag register following a synchronize (with data) mode command; enable an interrupt request and a bit setting in the interrupt status register when the time tag register rolls over from 0000 to ffff. assuming the time tag register is not loaded or reset, this will occur at approximately 4-second time intervals, for 64 interrupts the ace series components provide many programmable options for interrupt generation and handling. the interrupt out- put pin (int ) has three software programmable modes of oper- ation: a pulse, a level output cleared under software control, or a level output automatically cleared following a read of the interrupt status register. individual interrupts are enabled by the interrupt mask register. the host processor may easily determine the cause of the inter- rupt by using the interrupt status register. the interrupt status register provides the current state of the interrupt conditions. the interrupt status register may be updated in two ways. in the standard interrupt handling mode, a particular bit in the interrupt status register will be updated only if the condition exists and the corresponding bit in the interrupt mask register is enabled. in the enhanced interrupt handling mode, a particular bit in the interrupt status register will be updated if the condition exists regardless of the contents of the corresponding interrupt mask register bit. in any case, the respective interrupt mask register bit enables an interrupt for a particular condition. addressing, internal registers, and memory management the software interface of the bu-65170/61580 to the host processor consists of 17 internal operational registers for normal operation, an additional 8 test registers, plus 64k x 16 of shared memory address space. the bu-65170/61580's 4k x 16 of inter- nal ram resides in this address space. reference table 2 and 24. definition of the address mapping and accessibility for the ace's 17 non-test registers, and the test registers, is as follows: interrupt mask register is used to enable and disable interrupt requests for various conditions. configuration registers #1 and #2 are used to select the bu- 61580's mode of operation, and for software control of rt status word bits, active memory area, bc stop-on-error, rt memory management mode selection, and control of the time tag oper- ation. start/reset register is used for ? command ? type functions, such as software reset, bc/mt start, interrupt reset, time tag reset, and time tag register test. the start/reset register includes provisions for stopping the bc in its auto-repeat mode, either at the end of the current message or at the end of the cur- rent bc frame. bc/rt command stack pointer register allows the host cpu to determine the pointer location for the current or most recent message when the bu-61580 is in bc or rt modes. bc control word/rt subaddress control word register :in bc mode, it allows host access to the current, or most recent bc control word. the bc control word contains bits that select the active bus and message format, enable off-line self-test, mask- ing of status word bits, enable retries and interrupts, and spec- ify mil-std-1553a or -1553b error handling. in rt mode, this register allows host access to the current or most recent subaddress control word. the subaddress control word is used to select the memory management scheme and enable interrupts for the current message. the read/write accessibility can be used as an aid for testing the ace. http://www..net/ datasheet pdf - http://www..net/
6 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 time tag register maintains the value of a real-time clock. the resolu- tion of this register is programmable from among 2, 4, 8, 16, 32, and 64 interrupt status register mirrors the interrupt mask register and con- tains a master interrupt bit. it allows the host processor to determine the cause of an interrupt request by means of a single read operation. configuration registers #3, #4, and #5 are used to enable many of the bu-61580's advanced features. these include all the enhanced mode features; that is, all the functionality beyond that of the previous generation product, the bus-61559 advanced integrated mux hybrid with enhanced rt features (aim-hy'er). for all three modes, use of the enhanced mode enables the various read-only bits in configuration register #1. for bc mode, the enhanced mode features include the expanded bc control word and bc block status word, additional stop-on-error and stop-on- status set functions, frame auto-repeat, programmable intermessage gap times, automatic retries, expanded status word masking, and the capability to generate interrupts following the completion of any selected message. for rt mode, the enhanced mode features include the expanded rt block status word, the combined rt/selective message monitor mode, internal wrapping of the rtfail output signal (from the j chip) to the rtflag rt status word bit, the double buffering scheme for individual receive (broadcast) subaddresses, and the alternate (fully soft- ware programmable) rt status word. for mt mode, use of the enhanced mode enables use of the selective message monitor, the com- bined rt/selective monitor modes, and the monitor triggering capability. data stack address register is used to point to the current address location in shared ram used for storing message words (second command words, data words, rt status words) in the selective word monitor mode. frame time remaining register provides a read only indication of the time remaining in the current bc frame. the resolution of this register is 100 s/lsb. message time remaining register provides a read only indication of the time remaining before the start of the next message in a bc frame. the resolution of this register is 1 bc frame/rt last command/mt trigger word register: in bc mode, it programs the bc frame time, for use in the frame auto-repeat mode. the resolution of this register is 100 status word register and bit word registers provide read-only indi- cations of the bu-65170/61580's rt status and bit words. test mode registers 0-7: these registers may be used to facilitate pro- duction or maintenance testing of the bu-65170/61580 and systems incorporating the bu-65170/61580. table 2. address mapping address lines register description/accessibility hex a4 a3 a2 a1 a0 00 0 0 0 0 0 interrupt mask register (rd/wr) 01 0 0 0 0 1 configuration register #1 (rd/wr) 02 0 0 0 1 0 configuration register #2 (rd/wr) 03 0 0 0 1 1 start/reset register (wr) 03 0 0 0 1 1 bc/rt command stack pointer register (rd) 04 0 0 1 0 0 bc control word*/rt subaddress control word register (rd/wr) 05 0 0 1 0 1 time tag register (rd/wr) 06 0 0 1 1 0 interrupt status register (rd) 07 0 0 1 1 1 configuration register #3 (rd/wr) 08 0 1 0 0 0 configuration register #4 (rd/wr) 09 0 1 0 0 1 configuration register #5 (rd/wr) 0a 0 1 0 1 0 data stack address register (rd) * 0b 0 1 0 1 1 bc frame time remaining register ( rd) * 0c 0 1 1 0 0 bc time remaining to next message register (rd) * 0d 0 1 1 0 1 bc frame time * /rt last command/mt trigger word* register (rd/wr) 0e 0 1 1 1 0 rt status word register (rd) 0f 0 1 1 1 1 rt bit word register (rd) 10 1 0 0 0 0 test mode register 0 ? ? ? ? * not applicable to bu-65170/61571 table 3. interrupt mask register (read/write 00h) bit description 15(msb) reserved 14 ram parity error 13 bc/rt transmitter timeout 12 bc/rt command stack rollover 11 mt command stack rollover 10 mt data stack rollover 9 hs fail 8 bc retry 7 rt address parity error 6 time tag rollover 5 rt circular buffer rollover 4 bc control word/rt subaddress control word eom 3 bc end of frame 2 format error 1 bc status set/rt mode code/mt pattern trigger 0(lsb) end of message http://www..net/ datasheet pdf - http://www..net/
7 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 table 4. configuration register #1 (read/write 01h) bit bc function (bits 11-0 enhanced mode only) rt without alternate status rt with alternate status (enhanced only) monitor function (enhanced mode only bits 12-0) 15 (msb) rt/bc-mt (logic 0) (logic 1) (logic 1) (logic 0) 14 mt/bc-rt (logic 0) (logic 0) (logic 0) (logic 1) 13 current area b/a current area b/a current area a/b current area b/a 12 message stop-on-error message monitor enabled (mmt) message monitor enabled (mmt) message monitor enabled (mmt) 11 frame stop-on-error s10 trigger enabled word 10 status set stop-on-message busy s09 start-on-trigger 9 status set stop-on-frame service request s08 stop-on-trigger 8 frame auto-repeat subsystem flag s07 not used 7 external trigger enabled rtflag (enhanced mode only) s06 external trigger enabled 6 internal trigger enabled not used s05 not used 5 intermessage gap timer enabled not used s04 not used 4 retry enabled not used s03 not used 3 doubled/single retry not used s02 not used 2 bc enabled (read only) not used s01 monitor enabled(read only) 1 bc frame in progress (read only) not used s00 monitor triggered (read only) 0 (lsb) bc message in progress (read only) rt message in progress (enhanced mode only,read only) rt message in progress (read only) monitor active (read only) separate broadcast data 0(lsb) enhanced rt memory management 1 clear service request 2 level/pulse* interrupt request 3 interrupt status auto clear 4 load time tag on synchronize 5 clear time tag on synchronize 6 time tag resolution 0 (ttr0) 7 time tag resolution 1 (ttr1) 8 time tag resolution 2(ttr2) 9 256-word boundary disable 10 overwrite invalid data 11 rx sa double buffer enable 12 busy lookup table enable 13 ram parity enable (bu-61585/6 and bu-65621 only) 14 enhanced interrupts 15(msb) description bit table 5. configuration register #2 (read/write 02h) table 6. start/reset register (write 03h) bit description 15(msb) reserved ? ? ? ? ? ? http://www..net/ datasheet pdf - http://www..net/
8 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 command stack pointer 0 0(lsb) ? ? ? ? ? ? description bit table 7. bc/rt command stack pointer reg. (read 03h) rt-rt format broadcast format mode code format 1553a/b select 0(lsb) 1 2 3 eom interrupt enable 4 mask broadcast bit 5 off line self test 6 bus channel a/b 7 retry enabled 8 reserved bits mask 9 subsys flag bit mask terminal flag bit mask 11 10 subsys busy bit mask 12 service request bit mask 13 m.e. mask 14 reserved 15(msb) description bit bcst: memory management 0 (mm0) 0(lsb) bcst: memory management 1 (mm1) 1 bcst:memory management 2 (mm2) 2 tx: memory management 1 (mm1) bcst: circ buf int 3 bcst: eom int 4 rx: memory management 0 (mm0) 5 rx: memory management 1 (mm1) 6 rx: memory management 2 (mm2) 7 rx: circ buf int 8 rx: eom int 9 tx: memory management 0 (mm0) 10 tx: memory management 2 (mm2) 12 tx: circ buf int 13 tx: eom int 14 rx: double buffer enable 15(msb) description bit 11 table 9. rt subaddress control word (read/write 04h) time tag 0 0(lsb) ? ? ? ? ? ? description bit table 10. time tag register (read/write 05h) end of message 0(lsb) bc status set/rt mode code/mt pattern trigger 1 format error 2 mt command stack rollover bc end of frame 3 bc control word/rt subaddress control word eom 4 rt circular buffer rollover 5 time tag rollover 6 rt address parity error 7 bc retry 8 hs fail 9 mt data stack rollover 10 bc/rt command stack rollover 12 bc/rt transmitter timeout 13 ram parity error 14 master interrupt 15(msb) description bit 11 table 11. interrupt status register (read 06h) enhanced mode code handling 0(lsb) 1553a mode codes enable 1 rtfail-flag wrap enable 2 mt command stack size 0 busy rx transfer disable 3 illegal rx transfer disable 4 alternate status word enable 5 override mode t/r error 6 illegalization disabled 7 mt data stack size 0 8 mt data stack size 1 9 mt data stack size 2 10 mt command stack size 1 12 bc/rt command stack size 0 13 bc/rt command stack size 1 14 enhanced mode enable 15(msb) description bit 11 table 12. configuration register #3 (read/write 07h) table 8. bc control word register read/write 04h, (bu-61580 only) http://www..net/ datasheet pdf - http://www..net/
9 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 test mode 0 0(lsb) test mode 1 1 test mode 2 2 broadcast mask enable/xor latch rt address with config #5 3 mt tag gap option 4 valid busy/no data 5 valid m.e./no data 6 2nd retry alt/same bus 7 1st retry alt/same bus 8 retry if status set 9 retry if -a and m.e. 10 expanded bc control word enable 12 mode command override busy 13 inhibit bit word if busy 14 external bit word enable 15(msb) description bit 11 table 13. configuration register #4 (read/write 08h) rt address parity 0(lsb) rt address 0 1 rt address 1 2 expanded crossing enabled rt address 2 3 rt address 3 4 rt address 4 5 rt address latch/transparent (see note) 6 broadcast disabled 7 gap check enabled 8 response timeout select 0 9 response timeout select 1 10 external tx inhibit b, read only bu-65170/61580x6 12 external tx inhibit a, read only bu-65170/61580x6 13 logic ? 0 ? 14 12mhz clock select 15(msb) description bit 11 table 14. configuration register #5 (read/write 09h) notes for table 14: read only, logic ? 0 ? for 65170/61580, logic ? 1 ? for 65171/61581/61586. monitor data stack address 0 0(lsb) ? ? ? ? ? ? description bit table 15. monitor data stack address register (read/write 0ah) bc frame time remaining 0 0(lsb) ? ? ? ? ? ? description bit table 16. bc frame time remaining register (read/write 0bh) note: resolution = 1 ? ? ? ? ? ? description bit table 17. bc message time remaining register (read/write 0ch) note: resolution = 1 ? ? ? ? ? ? description bit table 18. bc frame time/rt last command/t trigger register (read/write 0dh) table 19. rt status word register (read/write 0eh) 11 bit description 15(msb) logic ? 0 ? 12 logic ? 0 ? 14 logic ? 0 ? 13 logic ? 0 ? 10 message error 9 instrumentation 8 service request 7 reserved 6 reserved 5 reserved 4 broadcast command received 3 busy logic ? 0 ? 2 subsystem flag 1 dynamic bus control accept 0(lsb) terminal flag http://www..net/ datasheet pdf - http://www..net/
10 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 command word contents error 0(lsb) rt-rt 2nd command word error 1 rt-rt no response error 2 transmitter shutdown b rt-rt gap/synch/address error 3 parity/manchester error received 4 incorrect sync received 5 low word count 6 high word count 7 channel b/a 8 terminal flag inhibited 9 transmitter shutdown a 10 handshake failure 12 loop test failure a 13 loop test failure b 14 transmitter timeout 15(msb) description bit 11 table 20. rt bit word register (read 0fh) invalid word 0(lsb) incorrect sync type 1 word count error 2 status set wrong status address/no gap 3 good data block transfer 4 retry count 0 5 retry count 1 6 masked status set 7 loop test fail 8 no response timeout 9 format error 10 error flag 12 channel b/a 13 som 14 eom 15(msb) description bit 11 table 21. bc mode block status word note: tables 21 to 24 are not registers, but they are words stored in ram. command word contents error 0(lsb) rt-rt 2nd command error 1 rt-rt gap/sync/address error 2 rt-rt format invalid word 3 incorrect sync 4 word count error 5 illegal command word 6 data stack rollover 7 loop test fail 8 no response timeout 9 format error 10 error flag 12 channel b/a 13 som 14 eom 15(msb) description bit 11 table 22. rt mode block status word gap time mode code 0(lsb) contiguous data/gap 1 channel b/a 2 command/data 3 error 4 broadcast 5 this rt 6 word flag 7 ? ? ? ? ? ? description bit 8 table 23. word monitor identification word command word contents error 0(lsb) rt-rt 2nd command error 1 rt-rt gap/sync/address error 2 rt-rt transfer invalid word 3 incorrect sync 4 word count error 5 reserved 6 data stack rollover 7 good data block transfer 8 no response timeout 9 format error 10 error flag 12 channel b/a 13 som 14 eom 15(msb) description bit 11 table 24. message monitor mode block status word http://www..net/ datasheet pdf - http://www..net/
11 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 bus controller (bc) architecture the bc protocol of the bu-61580 implements all mil-std- 1553b message formats. message format is programmable on a message-by-message basis by means of bits in the bc control word and the t/r bit of the command word for the respective message. the bc control word allows 1553 message format, 1553a/b type rt, bus channel, self-test, and status word mask- ing to be specified on an individual message basis. in addition, automatic retries and/or interrupt requests may be enabled or disabled for individual messages. the bc performs all error checking required by mil-std-1553b. this includes validation of response time, sync type and sync encoding, manchester ii encoding, parity, bit count, word count, status word rt address field, and various rt-to-rt transfer errors. the bu-61580's bc response timeout value is programmable with choices of 18, 22, 50, and 130 s. the longer response timeout values enable operation over long buses and/or the use of repeaters. figure 2 illustrates bc intermessage gap and frame timing. the bu-61580 may be programmed to process bc frames of up to 512 messages with no processor intervention. it is possible to program for either single frame or frame auto-repeat operation. in the auto-repeat mode, the frame repetition rate may be con- trolled either internally, using a programmable bc frame timer, or from an external trigger input. the internal bc frame time is pro- grammable up to 6.55 seconds in increments of 100 s. in addi- tion to bc frame time, intermessage gap time, measured from the start of the current message to the start of the subsequent message, is programmable on an individual message basis. the time between individual successive messages is programmable up to 65.5 ms, in increments of 1 s. bc memory organization table 25 illustrates a typical memory map for bc mode. it is important to note that the only fixed locations for the bu-61580 in the standard bc mode are for the two stack pointers (address locations 0100 (hex) and 0104) and for the two message count locations (0101 and 0105). enabling the frame auto-repeat mode will reserve four more memory locations for use in the enhanced bc mode; these locations are for the two initial stack pointers (address locations 102 (hex) and 106) and for the initial message count locations (103 and 107). the user is free to locate the stack and bc message blocks anywhere else within the 64k (4k internal) shared ram address space. for simplicity of illustration, assume the allocation of the maxi- mum length of a bc message for each message block in the typ- ical bc memory map of table 25. the maximum size of a bc message block is 38 words, for an rt-to-rt transfer of 32 data words (control + 2 commands + loopback + 2 status words + 32 data words). note, however, that this example assumes the disabling of the 256-word boundaries. message no. 1 message no. 2 message no. 1 message gap time for message no. 1 bc frame time intermessage gap time stack b not used message block 93 0f00-0fff 0efc-0eff 0ed6-0efb ? ? ? ? ? ? description address (hex) 0103 figure 2. bc message gap and frame timing note: used only in the enhanced bc mode with frame auto-repeat enabled. 0000-00ff table 25. typical bc memory organization (shown for 4k ram) 0100 http://www..net/ datasheet pdf - http://www..net/
12 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 bc memory management figure 3 illustrates the bu-61580's bc memory management scheme. one of the bc memory management features is the global double buffering mechanism. this provides for two sets of the various bc mode data structures: stack pointer and message counter locations, descriptor stack areas, and bc message blocks. bit 13 of configuration register #1 selects the current active area. at any point in time, the bu-61580's internal 1553 memory management logic may access only the various data structures within the ? active ? area. figure 3 delineates the ? active ? and ? inactive ? areas by the nonshaded and shaded areas, respectively; however, at any point in time, both the ?active? and ?nonactive? areas are accessible by the host processor . in most applications, the host processor will access the ? nonactive ? area, while the 1553 bus processes the ? active ? area messages. the bc may be programmed to transmit multimessage frames of up to 512 messages. the number of messages to be processed is programmable by the active area message count location in the shared ram, initialized by the host processor. in addition, the host processor must initialize another location, the active area stack pointer. the stack pointer references the four-word mes- sage block descriptor in the stack area of shared ram for each message to be processed. the bc stack size is programmable with choices of 256, 512, 1024, and 2048 words. in the bc frame auto-repeat mode, the initial stack pointer and initial message counter locations must be loaded by the host prior to the processing of the first frame. the single frame mode does not use these two locations. the third and fourth words of the bc block descriptor are the intermessage gap time and the message block address for the respective message. these two memory locations must be writ- ten by the host processor prior to the start of message process- ing. use of the intermessage gap time is optional. the block address pointer specifies the starting location for each message block. the first word of each bc message block is the bc control word. at the start and end of each message, the block status and time tag words write to the message block descriptor in the stack. the block status word includes indications of message in process or message completion, bus channel, status set, response timeout, retry count, status address mismatch, loop test (on-line self-test) failure, and other error conditions. table 21 illustrates the bit mapping of the bc block status word. the 16-bit time tag word will reflect the current contents of the inter- nal time tag register. this read/writable register, which oper- ates for all three modes, has programmable resolution of from 2 to 64 s/lsb. in addition, the time tag register may be clocked from an external source. bc message block formats and bc control word in bc mode, the bu-61580 supports all mil-std-1553 message formats. for each 1553 message format, the bu-61580 man- dates a specific sequence of words within the bc message 15 13 0 current area b/a configuration register 1 initial stack pointers (note) initial message counters (note) message counters stack pointers block status word time tag word message gap time word message block addr descriptor stacks message blocks message block message block note: initial stack pointers and initial message counters used only in bc frame auto-repeat mode. figure 3. bc mode memory management http://www..net/ datasheet pdf - http://www..net/
13 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 block. this includes locations for the control, command and (transmitted) data words that are to be read from ram by the bc protocol logic. in addition, subsequent contiguous locations must be allocated for storage of received loopback, rt status and data words. figure 4 illustrates the organization of the bc message blocks for the various mil-std-1553 message for- mats. note that for all of the message formats, the bc control word is located in the first location of the message block. for each of the bc message block formats, the first word in the block is the bc control word. the bc control word is not trans- mitted on the 1553 bus. instead, it contains bits that select the active bus and message format; enable off-line self-test; mask- ing of status word bits; enable retries and interrupts; and speci- fies mil-std-1553a or -1553b error handling. the bit mapping and definitions of the bc control word are illustrated in table 8. the bc control word is followed by the command word to be transmitted, and subsequently by a second command word (for an rt-to-rt transfer), followed by data words to be transmitted (for receive commands). the location after the last word to be transmitted is reserved for the loopback word. the loopback word is an on-line self-test feature. the subsequent locations after the loopback word are reserved for received status words and data words (for transmit commands). automatic retries the bu-61580 bc implements automatic message retries. when enabled, retries will occur, following response timeout or format error conditions. as additional options, retries may be enabled when the message error status word bit is set by a 1553a rt or following a ? status set ? condition. for a failed message, either one or two message retries will occur, the bus channel (same or alternate) is independently programmable for the first and sec- ond retry attempts. retries may be enabled or disabled on an individual message basis. bc interrupts bc interrupts may be enabled by the interrupt mask register for stack rollover, retry, end-of-message (global), end-of- message (in conjunction with the bc control word for individual messages), response timeout, message error, end of bc frame, and status set conditions. the definition of ? status set ? is pro- grammable on an individual message basis, by means of the bc control word. this allows for masking ( ? care/don't care ? ) of the individual rt status word bits. remote terminal (rt) architecture the rt protocol design of the bu-65170/61580 represents ddc's fifth generation implementation of a 1553 rt. one of the salient features of the ace's rt architecture is its true multipro- tocol functionality. this includes programmable options for sup- port of mil-std-1553a, the various mcair protocols, and mil- std-1553b notice 2. the bu-65170/61580 rt response time is 2 to 5 s dead time (4 to 7 s per 1553b), providing compliance to all the 1553 protocols. additional multiprotocol features of the bu-65170/61580 include options for full software control of rt status and built-in-test (bit) words. alternatively, for 1553b applications, these words may be formulated in real time by the bu-65170/61580 protocol logic. the bu-65170/61580 rt protocol design implements all the mil-std-1553b message formats and dual redundant mode codes. this design is based largely on previous generation prod- ucts that have passed seafac testing for mil-std-1553b com- pliance. the ace rt performs comprehensive error checking, word and format validation, and checks for various rt-to-rt transfer errors. other key features of the bu-65170/61580 rt bc-to-rt transfer control word receive command word data word #1 data word #2 . . . last data word last data word looped back status received last data word . . . data word #2 data word #1 status received transmit command looped back transmit command word control word rt-to-bc transfer transmit command looped back rx rt status word last data . . . data #2 data #1 tx rt status word transmit command receive command control word rt-to-rt transfer mode command looped back status received mode command control word mode code; no data mode command looped back data word status received tx mode command control word tx mode code; with data tx command looped back last data . . . data #2 data #1 tx rt status word tx command rx broadcast command control word rt-to-rts (broadcast) transfer last data status word last data . . . data #2 data #1 broadcast command control word broadcast data word data word looped back status received rx mode command control word rx mode code; with data broadcast mode command looped back broadcast mode command control word broadcast mode code; no data data word looped back data word broadcast mode command control word broadcast mode code; with data figure 4. bc message block formats http://www..net/ datasheet pdf - http://www..net/
14 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 include a set of interrupt conditions, internal command illegaliza- tion, and programmable busy by subaddress. rt memory organization table 26 illustrates a typical memory map for the bu-61580 in rt mode. as in bc mode, the two stack pointers reside in fixed locations in the shared ram address space: address 0100 (hex) for the area a stack pointer and address 0104 for the area b stack pointer. besides the stack pointer, for rt mode there are several other areas of the ace address space designated as fixed locations. all rt modes of operation require the area a and area b lookup tables. also allocated are several fixed locations for optional features: command illegalization lookup table, mode code selective interrupt table, mode code data table, and busy bit lookup table. it should be noted that any unen- abled optional fixed locations may be used for general purpose storage (data blocks). the rt lookup tables, which provide a mechanism for mapping data blocks for individual tx/rx/bcst-subaddresses to areas in the ram, occupy address range locations are 0140 to 01bf for area a and 01c0 to 023f for area b. the rt lookup tables include subaddress control words and the individual data block pointers. if used, address range 0300-03ff will be dedicated as the illegalizing section of ram. the actual stack ram area and the individual data blocks may be located in any of the nonfixed areas in the shared ram address space. rt memory management one of the salient features of the ace series products is the flex- ibility of its rt memory management architecture. the rt archi- tecture allows the memory management scheme for each trans- mit, receive, or broadcast subaddress to be programmable on a subaddress basis. also, in compliance with mil-std-1553b notice 2, the bu-65170/61580 provides an option to separate data received from broadcast messages from nonbroadcast received data. besides supporting a global double buffering scheme (as in bc mode), the ace rt provides a pair of 128-word lookup tables for memory management control. they are programmable on a subaddress basis (refer to table 27). these 128-word tables include 32-word tables for transmit message pointers and receive message pointers. there is also a third, optional lookup table for broadcast message pointers, providing notice 2 com- pliance, if necessary. the fourth section of each of the rt lookup tables stores the 32 subaddress control words (refer to table 9 and 28). the indi- vidual subaddress control words may be used to select the rt memory management option and interrupt scheme for each transmit, receive, and (optionally) broadcast subaddress. for each transmit subaddress, there are two possible memory management schemes: (1) single message; and (2) circular buffer. for each receive (and optionally broadcast) subaddress, there are three possible memory management schemes: (1) sin- gle message; (2) double buffered; and (3) circular buffer. for each transmit, receive and broadcast subaddress, there are two interrupt conditions that are programmable by the respective subaddress control word: (1) after every message to the sub- data block 100 ? ? ? ? ? ? description address (hex) 0105-0107 table 26. typical rt memory map (shown for 4k ram) table 27. look-up tables area a area b description comment 01c0 . . . 01df rx(/bcst)_sa0 . . . rx(/bcst)_sa31 receive (/broadcast) lookup table 01e0 . . . 01ff tx_sa0 . . . tx_sa31 transmit lookup table 0200 . . . 021f bcst_sa0 . . . bcst_sa31 broadcast lookup table optional 0220 . . . 023f sacw_sa0 . . . sacw_sa31 subaddress control word lookup table (optional) 0140 . . . 015f 0160 . . . 017f 0180 . . . 019f 01a0 . . . 01bf mm2 mm1 mm0 comment 0 0 0 single message or double buffered 0 0 1 128-word 0 1 0 256-word 0 1 1 512-word 1 1 1 1 1 1 0 0 1 0 1 0 8192-word 4096-word 2048-word 1024-word circular buffer of specified size description table 28. subaddress control word memory management subaddress buffer scheme http://www..net/ datasheet pdf - http://www..net/
15 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 address; (2) after a circular buffer rollover. an additional table in ram may be used to enable interrupts following selected mode code messages. when using the circular buffer scheme for a given subaddress, the size of the circular buffer is programmable by three bits of the subaddress control word (see table 28). the options for cir- cular buffer size are 128, 256, 512, 1024, 2048, 4096, and 8192 data words. single message mode figure 5 illustrates the rt single message memory manage- ment scheme. when operating the bu-65170/61580 in its ? aim- hy ? (default) mode, the single message scheme is implemented for all transmit, receive, and broadcast subaddresses. in the single message mode (also in the double buffer and circular buffer modes), there is a global double buffering scheme, con- trolled by bit 13 of configuration register #1. this selects from between the two sets of the various data structures shown in the figure: the stack pointers (fixed addresses), descriptor stacks (user defined addresses), rt lookup tables (fixed addresses), and rt data word blocks (user defined addresses). figures 5, 6, and 7 delineate the ? active ? and ? nonactive ? areas by the non- shaded and shaded areas, respectively. as shown, the ace stores the command word from each mes- sage received, in the fourth location within the message descrip- tor (in the stack) for the respective message. the t/r bit, subad- dress field, and (optionally) broadcast/own address, index into the active area lookup table, to locate the data block pointer for the current message. the bu-65170/61580 rt memory man- agement logic then accesses the data block pointer to locate the starting address for the data word block for the current mes- sage. the maximum size for an rt data word block is 32 words. for a particular subaddress in the single message mode, there is overwriting of the contents of the data blocks for receive/broad- cast subaddresses ? or overreading, for transmit subaddresses. in the single message mode, it is possible to access multiple data blocks for the same subaddress. this, however, requires the intervention of the host processor to update the respective lookup table pointer. to implement a data wraparound subaddress, as required by notice 2 of mil-std-1553b, the single message scheme should be used for the wraparound subaddress. notice 2 recommends subaddress 30 as the wraparound subaddress. circular buffer mode figure 6 illustrates the rt circular buffer memory management scheme. the circular buffer mode facilitates bulk data transfers. the size of the rt circular buffer, shown on the right side of the figure, is programmable from 128 to 8192 words (in even powers of 2) by the respective subaddress control word. as in the sin- gle message mode, the host processor initially loads the individ- ual lookup table entries. at the start of each message, the ace stores the lookup table entry in the third position of the respec- tive message block descriptor in the stack area of ram, as in the single message mode. the ace transfers receive or transmit data words to (from) the circular buffer, starting at the location referenced by the lookup table pointer. at the end of a valid (or optionally invalid) message, the value of the lookup table entry updates to the next location after the last address accessed for the current message. as a result, data words for the next message directed to the same tx/rx(/bcst) subaddress will be accessed from the next contiguous block of address locations within the circular buffer. as a recommended option, the lookup table pointers may be programmed to not update following an invalid receive (or broadcast) message. this allows the 1553 bus controller to retry the failed message, result- ing in the valid (retried) data overwriting the invalid data. this eliminates overhead for the rt's host processor. when the point- er reaches the lower boundary of the circular buffer (located at 128, 256, . . . 8192-word boundaries in the bu-65170/61580 address space), the pointer moves to the top boundary of the cir- cular buffer, as figure 6 shows. implementing bulk data transfers the use of the circular buffer scheme is ideal for bulk data trans- fers; that is, multiple messages to/from the same subaddress. the recommendation for such applications is to enable the cir- cular buffer interrupt request. by so doing, the routine transfer of multiple messages to the selected subaddress, including errors and retries, is transparent to the rt's host processor. by strate- gically initializing the subaddresses' lookup table pointer prior to the start of the bulk transfer, the bu-65170/61580 may be con- figured to issue an interrupt request only after it has received the anticipated number of valid data words to the designated sub- address. subaddress double buffering mode for receive (and broadcast) subaddresses, the bu-65170/61580 rt offers a third memory management option, subaddress double buffering. subaddress double buffering provides a means of ensuring data consistency. figure 7 illustrates the rt subaddress double buffering scheme. like the single message and circular buffer modes, the double buffering mode may be selected on a subaddress basis by means of the subaddress control word. the purpose of the double buffering mode is to provide the host processor a convenient means of accessing the most recent, valid data received to a given subaddress. this serves to ensure the highest possible degree of data consisten- cy by allocating two 32-bit data word blocks for each individual receive (and/or broadcast) subaddress. at a given point in time, one of the two blocks will be designated as the ? active ? 1553 data block while the other will be designat- ed as the ? inactive ? block. the data words from the next receive message to that subaddress will be stored in the ? active ? block. upon completion of the message, provided that the message was valid and subaddress double buffering is enabled, the bu- 65170/61580 will automatically switch the ? active ? and ? inactive ? blocks for the respective subaddress. the ace accomplishes this by toggling bit 5 of the subaddress's lookup table pointer and rewriting the pointer. as a result, the most recent valid block of received data words will always be readily accessible to the host processor. as a means of ensuring data consistency, the host processor is able to reliably access the most recent valid, received data word block by performing the following sequence: http://www..net/ datasheet pdf - http://www..net/
16 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 5. rt memory management: single message mode data blocks data block data block block status word time tag word data block pointer received command word descriptor stacks look-up table addr look-up table (data block addr) 15 13 0 current area b/a configuration register stack pointers (see note) note: lookup table is not used for mode commands when enchanced mode codes are enabled. figure 6. rt memory management: circular buffer mode circular buffer rollover 15 13 0 received (transmitted) message data (next location) 128, 256 8192 words pointer to current data block pointer to next data block look-up table entry circular data buffer look-up tables look-up table address block status word time tag word data block pointer received command word configuration register stack pointers descriptor stack current area b/a tx/rs/bcst_sa look-up table entry is updated following valid receive (broadcast) message or following completion of transit message. * * 15 13 0 block status word time tag word data block pointer received command word configuration register stack pointers descriptor stack current area b/a data blocks data block 1 data block 0 x..x 0 yyyyy x..x 1 yyyyy receive double buffer enable subaddress control word msb data block pointer look-up tables figure 7. rt memory management: subaddress double buffering mode http://www..net/ datasheet pdf - http://www..net/
17 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 (1) disable the double buffering for the respective subad- dress by the subaddress control word. that is, temporarily switch the subaddress' memory management scheme to the single message mode. (2) read the current value of the receive (or broadcast) sub- address's lookup table pointer. this points to the current ? active ? data word block. by inverting bit 5 of this pointer value, it is possible to locate the start of the ? inactive ? data word block. this block will contain the data words received during the most recent valid message to the subaddress. (3) read out the words from the ? inactive ? (most recent) data word block. (4) re-enable the double buffering mode for the respective subaddress by the subaddress control word. rt interrupts as in bc mode, the bu-65170/61580 rt provides many mask- able interrupts. rt interrupt conditions include end of (every) message, message error, selected subaddress (subaddress control word) interrupt, circular buffer rollover, selected mode code interrupt, and stack rollover. descriptor stack at the beginning and end of each message, the bu- 65170/61580 rt stores a four-word message descriptor in the active area stack. the rt stack size is programmable, with choices of 256, 512, 1024, and 2048 words. figures 5, 6 and 7 show the four words: block status word, time tag word, data block pointer, and the 1553 received command word. the rt block status word includes indications of message in-progress or message complete, bus channel, rt-to-rt transfer and rt-to- rt transfer errors, message format error, loop test (self-test) fail- ure, circular buffer rollover, illegal command, and other error con- ditions. table 22 shows the bit mapping of the rt block status word. as in bc mode, the time tag word stores the current contents of the bu-65170/61580's read/writable time tag register. the resolution of the time tag register is programmable from among 2, 4, 8, 16, 32, and 64 s/lsb. also, incrementing of the time tag counter may be from an external clock source or via software command. the ace stores the contents of the accessed lookup table loca- tion for the current message, indicating the starting location of the data word block, as the data block pointer. this serves as a convenience in locating stored message data blocks. the ace stores the full 16-bit 1553 command word in the fourth location of the rt message descriptor. rt command illegalization the bu-65170/61580 provides an internal mechanism for rt command illegalization. in addition, the busy status word bit can be set so that it is only a programmed subset of the trans- mit/receive/broadcast subaddresses. the illegalization scheme uses a 256-word area in the bu- 65170/61580's address space. a benefit of this feature is the reduction of printed circuit board requirements, by eliminating the need for an external prom, pld, or ram device that does the illegalizing function. the bu-j1165170/61580's illegalization scheme provides maximum flexibility, allowing any subset of the 4096 possible combinations of broadcast/own address, t/r bit, subaddress, and word count/mode code to be illegalized. another advantage of the ram-based illegalization technique is that it provides for a high degree of self-testability. addressing the illegalization table table 29 illustrates the addressing scheme of the illegalization ram. as shown, the base address of the illegalizing ram is 0300 (hex). the ace formulates the index into the illegalizing table based on the values of br o adcast /own address, t/r bit, subaddress, and the msb of the word count/mode code field (wc/mc4) of the current command word. the internal ram has 256 words reserved for command illegal- ization. broadcast commands may be illegalized separately from nonbroadcast receive commands and mode commands. commands may be illegalized down to the word count level. for example, a one-word receive command to subaddress 1 may be legal, while a two-word receive command to subaddress 1 may be illegalized. the first 64 words of the illegalization table refer to broadcast receive commands (two words per subaddress). the next 64 words refer to broadcast transmit commands. since nonmode code broadcast transmit commands are by definition invalid, this section of the table (except for subaddresses 0 and 31) does not need to be initialized by the user. the next 64 words correspond to nonbroadcast receive commands. the final 64 words refer to nonbroadcast transmit commands. messages with word count/ mode code (wc/mc) fields between 0 and 15 may be illegalized by setting the corresponding data bits for the respective even- numbered address locations in the illegalization table. likewise, messages with wc/mc fields between 16 and 31 may be ille- galized by setting the corresponding data bits for the respective odd-numbered address locations in the illegalization table. the following should be noted with regards to command illegal- ization: (1)to illegalize a particular word count for a given broad- cast/own address-t/r subaddress, the appropriate bit posi- tion in the respective illegalization word should be set to logic 1. a bit value of logic 0 designates the respective command word as a legal command. the ace will respond to an illegalized nonbroadcast command with the message error bit set in its rt status word. (2)for subaddresses 00001 through 11110, the ? wc/mc ? field specifies the word count field of the respective command word. for subaddresses 00000 and 11111, the ? wc/mc ? field specifies the mode code field of the respec- tive command word. (3)since nonmode code broadcast transmit messages are not defined by mil-std-1553b, the sixty (60) words in the illegalization ram, addresses 0342 through 037d, corre- sponding to these commands do not need to be initialized. the ace will not respond to a nonmode code broadcast transmit command, but will automatically set the message http://www..net/ datasheet pdf - http://www..net/
18 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 error bit in its internal status register, regardless of whether or not corresponding bit in the illegalization ram has been set. if the next message is a transmit status or transmit last command mode code, the ace will respond with its message error bit set. programmable busy as a means of providing compliance with notice 2 of mil-std- 1553b, the bu-65170/61580 rt provides a software controllable means for setting the busy status word bit as a function of sub- address. by a busy lookup table in the bu-65170/61580 address space, it is possible to set the busy bit based on com- mand broadcast/own address, t/r bit, and subaddress. another programmable option, allows received data words to be either stored or not stored for messages, when the busy bit is set. other rt functions the bu-65170/61580 allows the hardwired rt address to be read by the host processor. also, there are options for the rt flag status word bit to be set under software control and/or automatically following a failure of the loopback self-test. other software controllable rt options include software programmable rt status and rt bit words, automatic clearing of the service request status word bit following a transmit vector word mode command, capabilities to clear and/or load the time tag register following receipt of synchronize mode commands, options regarding data word transfers for the busy and/or message error (illegal) status word bits, and for handling of 1553a and reserved mode codes. monitor (mt) architecture the bu-61580 provides three bus monitor (mt) modes: (1) the ? aim-hy ? (default) or ? aim-hy'er ? word monitor mode. (2) a selective message monitor mode. (3) a simultaneous remote terminal/selective message monitor mode. the strong recommendation for new applications is the use of the selective message monitor, rather than the word monitor. besides providing monitor filtering based on rt address, t/r bit, and subaddress, the message monitor eliminates the need to determine the start and end of messages by software. the devel- opment of such software tends to be a tedious task. moreover, at run time, it tends to entail a high degree of cpu overhead. word monitor in the word monitor mode, the bu-61580 monitors both 1553 buses. after initializing the word monitor and putting it on-line the bu-61580 stores all command, status, and data words received from both buses. for each word received from either bus, the bu-61580 stores a pair of words in ram. the first word is the 16 bits of data from the received word. the second word is the monitor identification (id), or ? ta g ? word. the id word con- tains information relating to bus channel, sync type, word validi- ty, and interword time gaps. the bu-61580 stores data and id words in a circular buffer in the shared ram address space. table 23 shows the bit mapping for the monitor id word. monitor trigger word there is a trigger word register that provides additional flexibil- ity for the word monitor mode. the bu-61580 stores the value of the 16-bit trigger word in the mt trigger word register. the con- tents of this register represent the value of the trigger command word. the bu-61580 has programmable options to start or stop the word monitor, and/or to issue an interrupt request following receipt of the trigger command word from the 1553 bus. selective message monitor mode the bu-61580 selective message monitor provides features to greatly reduce the software and processing burden of the host cpu. the selective message monitor implements selective mon- itoring of messages from a dual 1553 bus, with the monitor fil- tering based on the rt address, t/r bit, and subaddress fields of received 1553 command words. the selective message monitor mode greatly simplifies the host processor software by distinguishing between command and status words. the selective message monitor maintains two stacks in the bu- 61580 ram: a command stack and a data stack. simultaneous rt/message monitor mode the selective message monitor may function as a purely passive monitor or may be programmed to function as a simultaneous rt/monitor. the rt/monitor mode provides complete remote terminal (rt) operation for the bu-61580's strapped rt address and bus monitor capability for the other 30 nonbroadcast rt addresses. this allows the bu-61580 to simultaneously operate as a full function rt and ? snoop ? on all or a subset of the bus activity involving the other rts on a bus. this type of operation is sometimes needed to implement a backup bus controller. the combined rt/selective monitor maintains three stack areas in the bu-61580 address space: an rt command stack, a monitor command stack, and a monitor data stack. the pointers for the various stacks have fixed locations in the bu-61580 address space. wc4/mc4 0(lsb) sa0 1 sa1 2 0 sa2 3 sa3 4 sa4 5 t/r 6 broadcast/own_address 7 1 8 1 9 0 10 0 12 0 13 0 14 0 15(msb) description bit 11 table 29. illegalization ram address definition http://www..net/ datasheet pdf - http://www..net/
19 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 selective message monitor memory organization table 30 illustrates a typical memory map for the ace in the selective message monitor mode. this mode of operation defines several fixed locations in the ram. these locations allo- cate in a manner that is compatible with the combined rt/selective message monitor mode. refer to table 30 for an example of a typical selective message monitor memory map. the fixed memory map consists of two monitor command stack pointers (location 102h and 106h), two monitor data stack pointers (locations 103h and 107h), and a selective message monitor lookup table (0280-02ffh) based on rt address, t/r , and subaddress. assume a monitor command stack size of 1k words, and a monitor data stack size of 2k words. refer to figure 8 for an illustration of the selective message monitor operation. upon receipt of a valid command word, the bu-61580 will reference the selective monitor lookup table (a fixed block of addresses) to check for the condition (disabled/enabled) of the current command. if disabled, the bu- 61580 will ignore (and not store) the current message; if enabled, the bu-61580 will create an entry in the monitor command stack at the address location referenced by the monitor command stack pointer. similar to rt mode, the ace stores a block status word, 16-bit time tag word, and data block pointer in the message descriptor, along with the received 1553 command word follow- ing reception of the command word. the ace writes the block status and time tag words at both the start and end of the mes- sage. the monitor block status word contains indications of message in-progress or message complete, bus channel, monitor data stack rollover, rt-to-rt transfer and rt-to-rt transfer errors, message format error, and other error conditions. table 24 shows the message monitor block status word. the data block pointer references the first word stored in the monitor data stack (the first word following the command word) for the current message. the bu-61580 will then proceed to store the subsequent words from the message (possible second command word, data word(s), status word(s)) into consecutive locations in the monitor data stack. the size of the monitor command stack is programmable to 256, 1k, 4k, or 16k words. the monitor data stack size is pro- grammable to 512, 1k, 2k, 4k, 8k, 16k, 32k, or 64k words. monitor interrupts may be enabled for monitor command stack rollover, monitor data stack rollover, and/or end-of-message conditions. in addition, in the word monitor mode there may be an interrupt enabled for a monitor trigger condition. processor and memory interface the ace terminals provide much flexibility for interfacing to a host processor and optional external memory. figure 1 shows that there are 14 control signals, 6 of which are dual purpose, for the processor/memory interface. figures 9 through 14 illus- trate six of the configurations that may be used for interfacing a 15 13 0 block status word time tag word data block pointer received command word configuration register #1 monitor command stack pointers monitor command stacks current area b/a monitor data stacks monitor data block #n + 1 monitor data block #n current command word monitor data stack pointers if this bit is "0" (not selected) no words are stored in either the command stack or data stack. in addition, the command and data stack pointers will not be updated. note selective monitor lookup tables selective monitor enable (see note) offset based on rta4-rta0, t/r, sa4 figure 8. selective message monitor memory management monitor command stack pointer b (fixed location) monitor data stack a 0800-0fff monitor command stack a 0400-07ff not used 0300-03ff selective monitor lookup table (fixed area) 0280-02ff not used 0108-027f monitor data stack pointer b (fixed location) 0107 not used 0104-0105 monitor data stack pointer a (fixed location) 0103 monitor command stack pointer a (fixed location) 0102 not used 0000-0101 description 0106 table 30. typical selective message monitor memory map (shown for 4k ram) address (hex) http://www..net/ datasheet pdf - http://www..net/
20 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 bu-65170 or bu-61580 to a host processor bus. the various possible configurations serve to reduce to an absolute minimum the amount of glue logic required to interface to 8-, 16-, and 32- bit processor buses. also included are features to facilitate inter- facing to processors that do not have a ? wait state ? type of hand- shake acknowledgement. finally, the ace supports a reliable interface to an external dual port ram. this type of interface minimizes the portion of the available processor bandwidth required to access the 1553 ram. the 16-bit buffered mode (figure 9) is the most common con- figuration used. it provides a direct, shared ram interface to a 16-bit or 32-bit microprocessor. in this mode, the ace's internal address and data buffers provide the necessary isolation between the host processor's address and data buses and the corresponding internal memory buses. in the buffered mode, the 1553 shared ram address space limit is the bu-65170/61580's 4k words of internal ram. the 16-bit buffered mode provides a pair of pin-programmable options: (1) the logic sense of the rd/wr control input is selectable by the polarity_sel input: for example, write when rd/wr is low for motorola 680x0 processors; write when rd/wr is high for the intel i960 series microprocessors. (2) by strapping the input signal zer o_w ait to logic "1," the ace terminals may interface to processors that have an acknowledge type of handshake input to accommodate hardware controlled wait states; most current processor chips have such an input. in this case, the bu-65170/61580 will assert its read yd output low only after it has latched write data internally or has presented read data on d15- d0. by strapping zer o_w ait to logic "0," it is possible to easily interface the bu-65170/61580 to processors that do not have an acknowledge type of handshake input. an example of such a processor is analog device's adsp2101 dsp chip. in this con- figuration, the processor can clear its strobe output before the completion of access to the bu-65170/61580 internal ram or register. in this case, read yd will go high following the rising edge of strbd and will stay high until completion of the trans- fer. read yd will normally be low when zer o_w ait is low. similar to the 16-bit buffered mode, the 16-bit transparent mode (figure 10) supports a shared ram interface to a host cpu. the transparent mode offers the advantage of allowing the buffer ram size to be expanded to up to 64k words, using exter- nal ram. a disadvantage of the transparent mode is that it requires external address and data buffers to isolate the proces- sor buses from the memory/bu-65170/61580 buses. a modified version of the transparent mode involves the use of dual port ram, rather than conventional static ram. refer to figure 11. this allows the host to access ram very quickly, the only limitation being the access time of the dual port ram. this configuration eliminates the bu-65170/61580 arbitration delays for memory accesses. the worst case delay time occurs only during a simultaneous access by the host and the bu- 65170/61580 1553 logic to the same memory address . in gen- eral, this will occur very rarely and the ace limits the delay to approximately 250 ns. figure 12 illustrates the connections for the 16-bit direct memory access (dma) mode. in this configuration the host processor, rather than the ace terminal, arbitrates the use of the address and data buses. the arbitration involves the two dma output signals request (dtreq ) and acknowledge (dt a ck ), and the input signal grant (dtgr t ). the dma interface allows the ace components to interface to large amounts of system ram while eliminating the need for external buffers. for system address spaces larger than 64k words, it is necessary for the host processor to provide a page register for the upper address bits (above a15) when the bu-65170/61580 accesses the ram (while asserting dt a ck low). the internal ram is accessible through the standard ace inter- face (select , strbd , read yd , etc). the host cpu may access external ram by the ace's arbitration logic and output control signals, as illustrated in figure 12. alternatively, control of the ram may be shared by both the host processor and the ace, as illustrated in figure 13. the latter requires the use of external logic, but allows the processor to access the ram directly at the full access speed of the ram, rather than waiting for the ace handshake acknowledge output (read yd ). figure 14 illustrates the 8-bit buffered mode. this interface allows a direct connection to 8-bit microprocessors and 8-bit microcontrollers. as in the 16-bit buffered configuration, the buffer ram limit is the bu-65170/61580's 4k words of internal ram. in the 8-bit mode, the host cpu accesses the bu- 65170/61580's internal registers and ram by a pair of 8-bit reg- isters embedded in the ace interface. the 8-bit interface may be further configured by three strappable inputs: zer o_w ait , polarity_sel, and trigger_sel. by connecting zer o_w ait to logic "0," the bu-65170/61580 may be interfaced with minimal "glue" logic to 8-bit microcontrollers, such as the intel 8051 series, that do not have an acknowledge type of hand- shake input. the programmable inputs polarity_sel and trigger_sel allow the bu-65170/61580 to accommodate the different byte ordering conventions and "a0" logic sense utilized by different 8-bit processor families. processor interface timing figures 15 and 16 illustrate the timing for the host processor to access the ace's internal ram or registers in the 16-bit, buffered, non-zero, wait-mode. figure 15 illustrates the 16-bit buffered, nonzero wait mode read cycle timing while figure 16 shows the 16-bit, buffered, nonzero wait mode write cycle timing. during a cpu transfer cycle, the signals strbd and select must be sampled low on the rising edge of the system clock to request access to the bu-65170/61580's internal shared ram. the transfer will begin on the first rising system clock edge when (select and strbd ) is low and the 1553 protocol/memory management unit is not accessing the internal ram. the falling edge of the output signal ioen indicates the start of the transfer. the ace latches the signals mem/reg and rd/wr internally on the first falling clock edge after the start of the transfer cycle. the address inputs latch internally on the first rising clock edge after the signal ioen goes low. note that the address lines may be latched at any time using the addr_lat input signal. the output signal read yd will be asserted low on the third ris- ing system clock edge after ioen goes low. the assertion of http://www..net/ datasheet pdf - http://www..net/
21 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 read yd low indicates to the host processor that read data is available on the parallel data bus, or that write data has been stored. at this time, the cpu should bring the signal strbd high, completing the transfer cycle. address latch timing figure 17 illustrates the operation and timing of the address input latches for the buffered interface mode. in the transparent mode, the address buffers are always transparent. since the transparent mode requires the use of external buffers, external address latches would be required to demultiplex a multiplexed address bus. in the buffered mode, however, the ace's internal address latches may be used to perform the demultiplexing func- tion. the addr_lat input signal controls address latch operation. when addr_lat is high, the outputs of the latch (which drive the ace's internal memory bus) track the state of address inputs a15 ? a00. when it is low, the internal memory bus remains latched at the state of a15 ? a00 just prior to the falling edge of addr_lat. miscellaneous self-test the bu-65170/61580 products incorporate several self-test fea- tures. these features include an on-line wraparound self-test for all messages in bc and rt modes, an off-line wraparound self- test for bc mode, and several other internal self-test features. the bc/rt on-line loop test involves a wraparound test of the encoder/decoder and transceiver. the bc off-line self-test involves the encoder/decoder, but not the transceiver. these tests entail checking the received version of every transmitted word for validity (sync, encoding, bit count, parity) and checking the received version of the last transmitted word for a bit-by-bit comparison with the encoded word. the loopback test also fails if there is a timeout of the internal transmitter watchdog timer. note that the timeout value of the watchdog timer depends on the mode of operation selected (1553a or 1553b). a failure of the loop test results in setting a bit in the message's block status word and, if enabled, will result in an interrupt request. with appropriate host processor software, the bc off-line test is able to exercise the parallel and serial data paths, encoder, decoder, and a substantial portion of the bc protocol and memory man- agement logic. there are additional built-in self-test features, that involve the use of three configuration register bits and the eight test regis- ters. this allows a test of approximately 99% of the j ? chip's inter- nal logic. these tests include an encoder test, a decoder test, a register test, a protocol test, and a test of the fail-safe (transmit- ter timeout) timer. there is also a test mode. in the test mode, the host processor can emulate arbitrary activity on the 1553 buses by writing to a pair of test registers. the test mode can be operated in conjunc- tion with the word monitor mode to facilitate end-to-end self- tests. ram parity generation and checking the architecture of the j ? monolithic is such that the amount of buffered ram may be extended beyond the 4k words of on-chip j ? ram. for this off-chip buffered ram, the j ? chip includes pro- visions to implement parity generation and checking. parity gen- eration and checking provides a mechanism for checking the data integrity of the internal, buffered memory. furthermore, 17- bit, rather than 16-bit, wide buffered ram would be used. for this ram, the j ? chip will generate the 17th bit (parity bit) for all (host and 1553) write accesses and check the parity bit for all read accesses. if a parity error occurs, an interrupt request may be issued, and the corresponding bit in the interrupt status register would be set. the bu-61585 incorporates an additional 8k x 17 ram chip. http://www..net/ datasheet pdf - http://www..net/
22 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 9. 16-bit buffered mode host ace 55 ? ? ? ? * additional address lines a12 and a13 are required with the bu-61585. http://www..net/ datasheet pdf - http://www..net/
23 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 10. 16-bit transparent mode host ace 55 ? ? ? ? http://www..net/ datasheet pdf - http://www..net/
24 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 11. 16-bit transparent mode using dual port ram host ace dual port ram cs-l wr-l oe-l cs-r wr-r oe-r memena-out memwr memoe busy-l busy-r n/c cpu d15-d0 cpu address dir '245 en '244 en d15-d0 a15-a0 cpu a4-a0 a4-a0 rd/wr rd/wr address decoder 1553 ram select 1553 reg select mem/reg ioen dtreq dtgrt dtack n/c select strbd cpu data strobe transparent/buffered +5v int cpu interrupt request readyd reset +5v mstclr cpu ready memena-in +5v http://www..net/ datasheet pdf - http://www..net/
25 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 12. 16-bit direct memory access (dma) mode host ace 55 ? ? ? ? http://www..net/ datasheet pdf - http://www..net/
26 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 13. 16-bit dma mode with external logic to reduce processor access time to external ram host ace 55 ? ? ? ? http://www..net/ datasheet pdf - http://www..net/
27 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 14. 8-bit buffered mode * additional address lines a12 and a13 are required with the bu-61585. host ace 55 ? ? ? ? http://www..net/ datasheet pdf - http://www..net/
28 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 15. cpu reading ram (shown for 16-bit, buffered, nonzero wait mode) clock in valid t7 t3 t8 t11 t13 t15 valid t10 t4 t9 t12 t19 valid t16 t17 select (note 2,7) (note 2) (note 3,4,7) (note 4,5) strbd mem/reg rd/wr ioen (note 2,6) (note 6) (note 6) (note 7,8,9) readyd a15-a0 d15-d0 t5 t1 t2 t6 t14 t18 http://www..net/ datasheet pdf - http://www..net/
29 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 notes for figure 15 and associated table. 1. for the 16-bit buffered nonzero wait configuration, transpa- rent/buffered must be connected to logic "0". zero_wait and dtreq/16/8 must be connected to logic "1". the inputs trig- ger_sel and msb/lsb may be connected to either +5 v or ground. 2. select and strbd may be tied together. ioen goes low on the first rising clk edge when select ? ref description min typ max units note reference t1 select and strbd low setup time prior to clock rising edge 10 ns notes 2, 10 t2 107.5 ns notes 2, 6 t2 t2 t2 3.7 128.3 2.8 s ns s notes 2, 6 notes 2, 6 notes 2, 6 t3 10 ns notes 3, 4, 5, 7 t3 20 ns notes 3, 4, 5, 7 t4 t4 address valid setup time following select and strbd low (@ 12 mhz) address valid setup time following select and strbd low (@ 16 mhz) 50 30 ns ns t6 t5 select hold time following ioen falling clock in rising edge delay to ioen falling edge 0 35 ns ns note 2 note 6 t9 t8 t7 address valid setup time prior to clock in rising edge mem/reg, rd/wr hold time prior to clock in falling edge mem/reg, rd/wr setup time prior to clock in falling edge 30 30 10 ns ns ns notes 7, 8, 9 notes 3, 4, 5, 7 notes 3, 4, 5, 7 t12 t12 t11 t11 t11 t11 t10 output data valid prior to readyd falling (@ 12 mhz) output data valid prior to readyd falling (@ 16 mhz) ioen falling delay to readyd falling (reading registers @ 12 mhz) ioen falling delay to readyd falling (reading registers @ 16 mhz) ioen falling delay to readyd falling (reading ram @ 12 mhz) ioen falling delay to readyd falling (reading ram @ 16 mhz) address hold time following clock in rising edge 54 33 235 170 235 170 30 250 187.5 250 187.5 265 205 265 205 ns ns ns ns ns ns ns note 6 note 6 notes 6, 10 notes 6, 10 notes 6, 10 notes 6, 10 notes 7, 8, 9, 10 select and strbd low delay to ioen low (uncontended access @ 16 mhz) select and strbd low delay to ioen low (contended access @ 16 mhz) select and strbd low delay to ioen low (contended access @ 12 mhz) select and strbd low delay to ioen low (uncontended access @ 12 mhz) mem/reg, rd/wr setup time following select and strbd low(@ 12 mhz) table for figure 15. cpu reading ram or registers (shown for 16-bit, buffered, nonzero wait mode) mem/reg, rd/wr setup time following select and strbd low(@ 16 mhz) note 6 ns 35 clock in rising edge delay to readyd falling t13 ns http://www..net/ datasheet pdf - http://www..net/
30 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 16. cpu writing ram (shown for 16-bit, buffered, nonzero wait mode) clock in t1 t6 t7 t2 t3 t18 t16 valid t8 t9 t14 t15 t17 valid t12 t10 t4 t11 t5 valid t13 select (note 2,7) (note 2) (note 3,4,7) (note 4,5) strbd mem/reg rd/wr ioen (note 2,6) (note 6) (note 9,10) (note 7,8,9,10) readyd a15-a0 d15-d0 http://www..net/ datasheet pdf - http://www..net/
31 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 ns 0 strbd valid high hold time from readyd rising edge t18 note 6 ns 30 strbd rising edge delay to ioen rising edge and readyd rising edge t17 ns note reference units max typ min description ref s 3.7 select and strbd low delay to ioen low (contended access @ 12 mhz) t2 table for figure 16. cpu writing ram or registers (shown for 16-bit, buffered, nonzero wait mode) 6. the timing for ioen, readyd and d15-d0 assumes a 50 pf load. for loading above 50 pf, the validity of ioen, readyd, and d15-d0 is delayed by an additional 0.14 ns/pf typ, 0.28 ns/pf max. 7. timing for a15-a0, mem/reg and select assumes addr-lat is connected to logic "1." refer to address latch timing for addition- al details. 8. internal ram is accessed by a11 through a0 (a13 through a0 for 61585 and 61586). registers are accessed by a4 through a0. 9. the address bus a15-a0 is internally buffered transparently until the first rising edge of clk after ioen goes low. after this clk edge, a15-a0 become latched internally. 10. setup time given for use in worst case timing calculations. none of the ace input signals are required to be synchronized to the system clock. for ace applications only, where select and strbd do not meet the setup time of t1, but occur during the setup window of an internal flip-flop, an additional clock cycle will be inserted between the falling clock edge that latches mem/reg and rd/wr and the rising clock edge that latches the address (a15-a0) and data (d15-d0). when this occurs, the pulse width of ioen falling to readyd falling (t14) increases by one clock cycle and the address hold time (t12 + t13) must be increased be one clock cycle. notes for figure 16 and associated table. 1. for the 16-bit buffered nonzero wait configuration, transpa- rent/buffered must be connected to logic "0". zero_wait and dtreq/16/8 must be connected to logic "1". the inputs trig- ger_sel and msb/lsb may be connected to either +5 v or ground. 2. select and strbd may be tied together. ioen goes low on the first rising clk edge when select ? http://www..net/ datasheet pdf - http://www..net/
32 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 17. address latch timing select msb/lsb mem/reg (1) (2) (3) (4) (5) (1) (2) (3) (4) t4 t5 a15-a0 addr_lat select msb/lsb mem/reg a15-a0 input signals internal values t1 t3 t2 table for figure 17. address latch timing ref description min typ max units t1 addr_lat pulse width 20 ns t2 addr_lat high delay to internal signals valid 10 ns t3 propagation delay from external input signals to internal signals valid 10 ns t5 t4 input hold time following falling edge of addr_lat input setup time prior to falling edge of addr_lat 20 10 ns ns notes for figure 17 and associated table. 1. applicable to buffered mode only. address select and mem/reg latches are always transparent in the transparent mode of operati on. 2. latches are transparent when addr_lat is high. internal values do not update when addr_lat is low. 3. msb/lsb input signal is applicable to 8-bit mode only (16/8 input = logic ? 0 ? ). msb/lsb input is a ? don ? t care ? for 16-bit operation. http://www..net/ datasheet pdf - http://www..net/
33 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 interface to mil-std-1553 bus figure 18 illustrates the interface from the various versions of the ace series terminals to a 1553 bus. the figure also indicates connections for both direct (short stub) and transformer (long stub) coupling, plus the peak-to-peak voltage levels that appear at various points (when transmitting). table 31 lists the characteristics of the required isolation trans- formers for the various ace terminals, the ddc and beta transformer technology corporation corresponding part num- ber, and the mil (desc) drawing number (if applicable). beta transformer technology is a direct subsidiary of ddc. for both coupling configurations, the isolation transformer is the transformer that interfaces directly to the ace component. for the transformer (long stub) coupling configuration, the trans- former that interfaces the stub to the bus is the coupling trans- former. the turns ratio of the isolation transformer varies, depending upon the peak-to-peak output voltage of the specific ace terminal. the transmitter voltage of each model of the bu-65170/61580 varies directly as a function of the power supply voltage. the turns ratios of the respective transformers will yield a secondary voltage of approximately 28 volts peak-to-peak on the outer taps (used for direct coupling) and 20 volts peak-to-peak on the inner taps (used for stub coupling). in accordance with mil-std-1553b, the turns ratio of the cou- pling transformer is 1.0 to 1.4. both coupling configurations require an isolation resistor to be in series with each leg con- necting to the 1553 bus; this protects the bus against short cir- cuit conditions in the transformers, stubs, or terminal compo- nents. notes for table 31 and figure 18: (1) shown for one of two redundant buses that interface to the bu-65170 or bu- 61580. (2) transmitted voltage level on 1553 bus is 6 vp-p min, 7 vp-p nominal, 9 vp-p max. (3) required tolerance on isolation resistors is 2%. instantaneous power dissipa- tion (when transmitting) is approximately 0.5 w (typ), 0.8 w (max). (4) transformer pin numbering is correct for the ddc (e.g., bus-25679) trans- formers. for the beta transformers (e.g., b-2203) or the qpl-21038-31 transform- ers (e.g., m21038/27-02), the winding sense and turns ratio are mechanically the same, but with reversed pin numbering; therefore, it is necessary to reverse pins 8 and 4 or pins 7 and 5 for the beta or qpl transformers (note: ddc transformer part numbers begin with a bus- prefix, while beta transformer part numbers begin with a b- prefix). (5)the b-2204, b-2388, and b-2344 transformers have a slightly different turns ratio on the direct coupled taps then the turns ratio of the bus-29854 direct cou- pled taps. they do, however, have the same transformer coupled ratio. for trans- former coupled applications, either transformer may be used. the transceiver in the bu-65170x2 and the bu-61580x2 was designed to work with a 1:0.83 ratio for direct coupled applications. for direct coupled applications, the 1.20:1 turns ration is recommended, but the 1.25:1 may be used. the 1.25:1 turns ratio will result in a slightly lower transmitter amplitude. (approximately 3.6% lower) and a slight shift in the ace's receiver threshold. table 31. isolation transformer guide recommended xformer turns ratio ace part number surface mount plug-in xformer coupled direct coupled bus-25679, b-2203, m21038/27 -03 2:1 1.41:1 lpb-5001 lpb-5008 lpb-6001 lpb-6008 bus-29854 b-2204, m21038/27 -03 1:0.6 1.20:1 1.25:1 (note 5) see table 32 1:1.79 1:2.5 bu-65170x1 bu-65171x1 bu-61580x1 bu-61581x1 bu-61585x1 bu-61586x1 bu-65170x3 bu-65171x3 bu-61580x3 bu-61581x3 bu-61585x3 bu-61586x3 bu-65170x6 bu-65171x6 bu-61580x6 bu-61581x6 bu-61585x6 bu-61586x6 bu-65170x2 bu-65171x2 bu-61580x2 bu-61581x2 bu-61585x2 bu-61586x2 b-2387 m21038/27 -12, m21038/27 -17 lpb-5002 lpb-5009 lpb-6002 lpb-6009 b-2388 m21038/27 -13, b-2334, m21038/27 -18 http://www..net/ datasheet pdf - http://www..net/
34 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 transformers in selecting isolation transformers to be used with the x3, x6 ace, there is a limitation on the maximum amount of leakage inductance. if this limit is exceeded, the transmitter rise and fall times may increase, possibly causing the bus amplitude to fall below the minimum level required by mil-std-1553. in addition, an excessive leakage imbalance may result in a transformer dynamic offset that exceeds 1553 specifications. the maximum allowable leakage inductance is 6.0 h, and is measured as follows: the side of the transformer that connects to the ace is defined as the ? primary ? winding. if one side of the primary is shorted to the primary center-tap, the inductance should be measured across the ? secondary ? (stub side) winding. this inductance must be less than 6.0 h. similarly, if the other side of the pri- mary is shorted to the primary center-tap, the inductance mea- sured across the ? secondary ? (stub side) winding must also be less than 6.0 h. the difference between these two measurements is the ? differential ? leakage inductance. this value must be less than 1.0 h. beta transformer technology corporation (bttc), a subsidiary of ddc, manufactures transformers in a variety of mechanical configurations with the required turns ratios of 1:2.5 direct cou- pled, and 1:1.79 transformer coupled. table 32 provides a list- ing of many of these transformers.for further information, con- tact bttc at 631-244-7393 or at www.bttc-beta.com. dlp-7014 slp-8007 slp-8024 not recommended lpb-5015 b-3310 hlp-6015 dual epoxy transformer, side by side, surface mount, 0.930" x 0.630", 0.155" max height dlp-7115 (see note 2) dual epoxy transformer, side by side, surface mount, 1.410" x 0.750", 0.130" max height single metal transformer, hermetically sealed, surface mount, 0.630" x 0.630", 0.175" max height b-3261 hlp-6014 dual epoxy transformer, side by side, flat pack, 0.930" x 0.630", 0.155" max height single metal transformer, hermetically sealed, flat pack, 0.630" x 0.630", 0.175" max height b-3300 dual epoxy transformer, side by side, through-hole, 0.930" x 0.630", 0.155" max height tst-9027 dual epoxy transformer, twin stacked, flat pack, 0.625" x 0.625", 0.280" max height tst-9017 dual epoxy transformer, twin stacked, surface mount, 0.625" x 0.625", 0.280" max height tst-9007 dual epoxy transformer, twin stacked, 0.625" x 0.625", 0.280" max height b-3819 lpb-5014 single epoxy transformer, surface mount, hi-temp solder, 0.625" x 0.625", 0.220" max height. may be used with bu-6xxxxx4 versions of the enhanced mini-ace.b-3819 single epoxy transformer, flat pack, 0.625" x 0.625", 0.150" max height b-3227 single epoxy transformer, surface mount, 0.625" x 0.625", 0.275" max height b-3231 single epoxy transformer, flat pack, 0.625" x 0.625", 0.275" max height b-3818 b-3067 b-3226 single epoxy transformer, through-hole, 0.625" x 0.625", 0.220" max height. may be used with bu-6xxxxx4 versions of the enhanced mini-ace. single epoxy transformer, through-hole, 0.625" x 0.625", 0.250" max height bttc part no. transformer configuration single epoxy transformer, surface mount, 0.625" x 0.625", 0.150" max height b-3229 single epoxy transformer, through hole, transformer coupled only, 0.500" x 0.350", 0.250" max height table 32. bttc transformers for use with x3, x6 ace notes: 1. for the bu-6xxxxx3/6 versions of the ace with -1553b transceivers, any of the transformers listed in the table may be used. 2. dlp-7115 operates to +105 c max. all other transformers listed operate to +130 c max. http://www..net/ datasheet pdf - http://www..net/
35 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 note: the bu-65170xx, bu-65171xx, bu-61581xx, bu-61585xx and bu-61586xx models are interfaced the same as the corresponding bu-6 1580xx model is shown (i.e. the bu-65170x1 is interfaced the same as the bu-61580x1). figure 18. bu-65170/61580 interface to a 1553 bus bu-61580x1 55 ? ? ? ? ? ? ? ? http://www..net/ datasheet pdf - http://www..net/
36 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 signal name processor/memory interface and control (15) description transparent/ b uffered (1) 64 strbd (1) 4 strobe data. used with select to initiate and control the data transfer cycle between the host processor and the bu- 65170/61580. select (1) 3 generally connected to a cpu address decoder output to select the bu-65170/61580 for a transfer to/from either ram or register. may be tied to strbd . mem/reg (1) 5 memory/register. generally connected to either a cpu address line or address decoder output. selects between mem- ory access (mem/reg = 1 ) or register access (mem/reg = 0 ). 6 tri-state control for external address and data buffers. generally not needed in the buffered mode. when low, external buffers should be to allow the host processor access to the bu-65170/61580 ? s ram and registers. 67 read yd (0) 66 int (o) 65 interrupt request output. if the level/pulse interrupt bit (bit 3) of configuration register #2 is low, a negative pulse of approximately 500 ns in width is output on int . if bit 3 is high, a low level interrupt request output will be asserted on int . dtreq (o) /16/8 (i) 31 dtgr t (i) /msb/lsb (i) 26 32 memena-out (o) 28 memory enable output. asserted low during both host processor and 1553 protocol/memory management memory transfer cycles. used as a memory chip select (cs ) signal for external ram in the transparent mode. 33 memoe (o)/ addr_lat (i) 29 memwr (o) /zer o_w ait (i) 30 rd/wr (1) used to select between the transparent/ dma mode (when strapped to logic 1) and the buffered mode (when strapped to logic 0) for the host processor interface. ioen (0) handshake output to host processor. for a nonzero wait state read access, signals that data ia available to be read on d15 through d0. for a nonzero wait state write cycle, signals the completion of data transfer to a register or ram loca- tion in the buffered zero wait state mode, active high output signal (following the rising edge of strbd ) used to indi- cate the latching of address and data (write only) and that an internal transfer between the address/data latches and the ram/registers is on-going. data transfer grant or most significant byte/least significant byte. in transparent mode, active low input signal assert- ed, in response to the dtreq output, to indicate that access to the processor buses has been granted to the bu- 65170/61580. in 8-bit buffered mode, input signal used to indicate which byte is being transferred (msb or lsb). the polarity_sel input controls the logic sense of msb/lsb. (note: only the 8-bit buffered mode uses msb/lsb.) see description of polarity_sel signal. n/c in 16-bit buffered mode. dt a ck (o)/ polarity_sel (i) data transfer acknowledge or polarity select. in transparent mode, active low output signal used to indicate acceptance of the processor interface bus in response to a data transfer grant (dtgr t ).in 16-bit buffered mode (transparent/ buffered = logic 0 and 16/8 = logic 1), input signal used to control the logic sense of the rd/wr signal. when polarity_sel is logic 1, rd/wr must be asserted high (logic 1) for a read operation and low (logic 0) for a write operation. when polarity_sel is logic 0, rd/wr must be asserted low (logic 0) for a read operation and high (logic 1) for a write operation.in 8-bit buffered mode (transparent/buffered = logic 0 and 16/8 = logic 0), input signal used to control the logic sense of the msb/lsb signal. when polarity_sel is logic 0, msb/lsb must be asserted low (logic 0) to indicate the transfer of the least significant byte and high (logic 1) to indicate the transfer of the most si g- nificant byte. when polarity_sel is logic 1, msb/lsb must be asserted high (logic 1) to indicate the transfer of the least significant byte and low (logic 0) to indicate the transfer of the most significant byte. memena-in (i) /trigger_sel (i) memory enable input or trigger select. in transparent mode, memena-in is an active low chip select (cs ) input to the 4k x 16 of internal shared ram. when only using internal ram, connect directly to memena-out . in 8-bit buffered mode, the input signal (trigger_sel) indicates the order of byte pairs transfer to or from the bu-65170/61580 by the host processor. this signal has no operation (can be n/c) in the 16-bit buffered mode.in the 8-bit buffered mode, trig- ger_sel should be asserted high (logic 1) if the byte order for both read operations and write operations is msb fol- lowed by lsb. trigger_sel should be asserted low (logic 0) if the byte order for both read operations and write oper- ations is lsb followed by msb. memory output enable or address latch. in transparent mode, memoe output will be used to enable data outputs for external ram read cycles (normally connected to the oe signal on external ram chips). in buffered mode, addr_lat input will be used to configure the internal address latches in latched mode (when low) or transparent mode (when high). memory write or zero wait state. in transparent mode, active low output signal (memwr ) will be asserted low during memory write transfers to strobe data into internal or external ram (normally connected to the wr signal on external ram chips). in buffered mode, input signal (zer o_w ait ) will be used to select between the zero wait mode (zer o_w ait = logic 0) and the nonzero wait mode (zer o_w ait = logic 1). data transfer request or 16-bit/8-bit transfer mode select. in transparent mode, active low output signal used to request access to the processor interface bus (address,data, and control buses). in buffered mode, input signal used to select between the 16-bit data transfer mode (16/8 = logic 1) and the 8 bit data transfer mode (16/8 = logic 0). pin read/write. for host processor access, selects either reading or writing. in the 16-bit buffered mode, if polarity select is logic ), then rd/wr is low (logic 0 ) for read accesses and high (logic 1 ) for write accesses. if polarity select is logic 1 or the configuration of the interface is a mode other than 16-bit buffered mode, then rd/wr is high (logic 1 ) for read accesses and low (logic 0 ) for write accesses. table 33. signal descriptions for bu-65170/61571, bu-61580/61585, bu-61586 (g, s or v package) http://www..net/ datasheet pdf - http://www..net/
37 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 table 33. signal descriptions for bu-65170/61571, bu-61580/61585, bu-61586 (g, s or v package) (continued) miscellaneous (7) option for bu-65170/61580x6 and the bu-61585x6. inhibits (disables) the respective (a/b) mil-std-1553 transmitter when asserted to logic ? 1. ? 36 70 tx_inh_a (i) external time tag clock input. use may be designated by bits 7, 8, and 9 of configuration register #2. when used it incre- ments the internal time tag register/counter. if not used, should be connected to +5v or ground. 63 tag_clk (i) 27 ssfla g (i)/ ext_trig (i) 45 incmd (o) master clear. negative true reset input, normally asserted low following power turn-on. requires a minimum 100ns nega- tive pulse to reset all internal logic to its ? power turn-on ? state. 7 mstclr (i) 16mhz (or 12mhz) clock input. 19 clock in (i) description pin signal name in command. in bc mode, asserted low throughout processing cycle for each message. in rt mode or message monitor mode, asserted low following receipt of command word and kept low until completion of current message sequence. in word monitor mode, goes low following monitor start command, kept low while monitor is on-line, goes high following reset command. subsystem flag or external trigger input. in the remote terminal mode, asserting this input , will set the subsystem flag bit in the bu-65170/61580's rt status word. a low on the ssflag input overrides a logic ? 1" of the respective bit (bit 8) of configuration register #1. in the bus controller mode, an enabled external bc start option (bit 7 of configuration register #1) and a low-to-high transition on this input will issue a bc start command, starting execution of the current bc frame. in the word monitor mode, an enabled external trigger (bit 7 of configuration register #1) and a low-to-high transition on this input will issue a monitor trigger. tx_inh_b (i) power and ground (8) -15(-12)vb ch. b transceiver ground 37 gndb ch. b +5v supply 38 ch. b -15v(-12v) supply* 36 +5vb ch. a transceiver ground 69 gnda ch. a +5v supply 68 +5va ch. a -15v(-12v) supply* 70 -15(-12)va logic ground 18 logic gnd logic +5v supply 54 +5v logic description pin signal name rt address (6) rtadp (i) 44 39 rtad0 (lsb) (i) 40 rtad1 (i) remote terminal address inputs 41 rtad2 (i) 42 rtad3 (i) 43 rtad4 (msb) (i) description pin signal name 1553 isolation transformer interface (4) analog transmit/receive input/outputs. connect directly to 1553 isolation transformers. 35 tx/rx-b (i/o) 34 tx/rx-b (i/o) 2 tx/rx-a (i/o) 1 tx/rx-a (i/o) description pin signal name note: * no connects (n/cs) for bu-65170/61580 and tx_inh input for bu-65170/61580x6. remote terminal address parity. must provide odd parity sum with rtad4-rtad0 in order for the rt to respond to non- broadcast commands. http://www..net/ datasheet pdf - http://www..net/
38 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 table 33. signal descriptions for bu-65170/61571, bu-61580/61585, bu-61586 (g, s or v package) (continued) address bus (16) a04 a10 21 13 16-bit bidirectional address bus. in both the buffered and transparent modes, the host cpu accesses the bu-65170/61580 registers and 4k words of internal ram by a11 through a0 (bu-61585 uses a13 through a0). the host cpu performs register selection by a4 through a0.in the buffered mode, a15-a0 are inputs only. in the transparent mode, a15-a0 are inputs during cpu accesses and drive outward (towards the cpu) when the 1553 protocol/memory management logic accesses up to 64k x 16 of external ram. the address bus drives outward only in the transparent when the signal dtack is low (indicating that the 61580 has control of the processor interface bus) and ioen is high (indicating that this is not a cpu access). most of the time, including immediately after power turn-on reset, the a15-a0 outputs will be in their disabled (high impedance) state. 25 20 12 a00 a05 a11 24 17 11 a01 a06 a12 23 16 10 a02 a07 a13 22 15 9 a03 a08 a14 14 8 a09 a15 (msb) description 16-bit bidirectional data bus. this bus interfaces the host processor to the internal registers and 4k words of ram(12k of ram for the bu-61585). in addition, in the transparent mode, this bus allows data transfers to take place between the internal protocol/memory management logic and up to 64k x 16 of external ram. most of the time, the outputs for d15 through d0 are in their high impedance state. they drive outward in the buffered or transparent mode when the host cpu reads the internal ram or registers. or, in the transparent mode, when the protocol/memory management logic is accessing (either reading or writing) internal ram or writing to external ram. 46 d10 d00 47 d01 48 d02 49 d03 d04 50 51 d05 52 d06 53 d07 55 d08 56 57 d09 58 d11 59 d12 60 d13 61 d14 62 d15 (msb) data bus (16) description pin signal name signal name pin http://www..net/ datasheet pdf - http://www..net/
39 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 tx/rx-b -va (see note) tx/rx-b gnda 34 69 +5va 33 68 dt a ck /polarity_sel ioen 32 67 dtreq /16/8 read yd 31 66 memwr /zer o_w ait int 30 65 memoe /addr_lat transparent/b uffered 29 64 memena_out tag_clk 28 63 ssfla g /ext_trig d15 27 62 dtgr t /msb/lsb d14 26 61 a00 d13 25 60 a01 d12 24 59 a02 d11 23 58 a03 d10 22 57 a04 d09 21 56 a05 d08 20 55 clk +5v logic 19 54 gnd d07 18 53 a06 d06 17 52 a07 d05 16 51 d04 a08 15 50 a09 d03 14 49 a10 d02 13 48 a11 d01 12 47 a12 d00 11 46 a13 incmd 10 45 a14 rtadp 9 44 a15 rtad4 8 43 mstclr rtad3 7 42 rd/wr rtad2 6 41 mem/reg rtad1 5 40 strbd rtad0 4 39 select +5vb 3 38 tx/rx-a gndb 2 37 tx/rx-a -vb (see note) 1 36 name name pin 35 70 notes: -15v for bu-65170/61580x1. -12v for bu-65170/61580x2. n/c for bu-65170/61580x3. for bu-65170/61580x6. pin 36 is tx_inh_b pin 70 is tx_inh_a memena_in /trigger_sel pin table 34. bu-65170/65171, bu-61580/61581/61585/61586 pin listings (g, s or v package) http://www..net/ datasheet pdf - http://www..net/
40 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 19. bu-65170/65171/61580/61581/61585/61586s mechanical outline 1.000 max (25.4) 0.400 (10.16) 1.700 (43.18) index denotes pin 1 0.215 (5.46) max for "d" package 0.165 (4.19) max for "s" package notes: 1. dimensions are in inches (millimeters). 2. package material: alumina (al 2 o 3 ). 3. lead material: kovar, plated by 150 http://www..net/ datasheet pdf - http://www..net/
41 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 20. bu-65170/65171/61580/61581/61585/61586v mechanical outline 70 36 35 1 0.018 http://www..net/ datasheet pdf - http://www..net/
42 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 figure 21. bu-65170/65171/61580/61581/61585/61586g mechanical outline 70 36 35 1 1.000 (max) 1.900 max 0.018 http://www..net/ datasheet pdf - http://www..net/
43 data device corporation www.ddc-web.com bu-65170/61580/61585 h1 web-09/02-0 ordering information bu-xxxxx xx-xxxx supplemental process requirements: s = pre-cap source inspection l = pull test q = pull test and pre-cap inspection k = one lot date code w = one lot date code and precap source y = one lot date code and 100% pull test z = one lot date code, precap source and 100% pull test blank = none of the above test criteria: 0 = standard testing 2 = mil-std-1760 amplitude compliant - applies to +5 volt transceiver option only process requirements: 0 = standard ddc practices, no burn-in (see following page.) 1 = mil-prf-38534 compliant 2 = b* 3 = mil-prf-38534 compliant with pind testing 4 = mil-prf-38534 compliant with solder dip 5 = mil-prf-38534 compliant with pind testing and solder dip 6 = b* with pind testing 7 = b* with solder dip 8 = b* with pind testing and solder dip 9 = standard ddc processing with solder dip, no burn-in (see following page.) temperature range/data requirements: 1 = -55 c to +125 c 2 = -40 c to +85 c 3 = 0 c to +70 c 4 = -55 c to +125 c with variables test data 5 = -40 c to +85 c with variables test data 8 = 0 c to +70 c with variables test data voltage/transceiver option: 0 = transceiverless 1 = +5 volts and -15 volts (1760 compliant - standard configuration) 2 = +5 volts and -12 volts 3 = +5 volts, rise/fall times=100 to 300 ns (-1553b)(see test criteria - 1760 compliant with option -xx2) 5 = +5/+15/-15v sinusoidal (mcair) 6 = +5 volts only with tx inhibit inputs brought out on negative supply pins package type: g = ? gull wing ? (formed lead) j = j lead (solder dip not available ) p = pga s = small dip v = very small flat pack product type: 65170 = 70-pin rt 65171 = 70-pin rt with latchable rt address option 61580 = 70-pin bc/rt/mt 61581 = 70-pin bc/rt/mt with latchable rt address option 61585 = 70-pin bc/rt/mt 8k x 17 with ram 61586 = 70-pin bc/rt/mt 8k x 17 with ram and rt address option note: the ace series is also available to desc drawing number 5962-93065. *standard ddc processing with burn-in and full temperature test, see table on following page. http://www..net/ datasheet pdf - http://www..net/
44 standard ddc processing test mil-std-883 method(s) condition(s) inspection 2009, 2010, 2017, and 2032 ? seal 1014 a and c temperature cycle 1010 c constant acceleration 2001 a burn-in 1015, table 1 ? printed in the u.s.a. data device corporation registered to iso 9001 file no. a5976 r e g i s t e r e d f i r m ? u h1 web-09/02-0 105 wilbur place, bohemia, new york, u.s.a. 11716-2482 for technical support - 1-800-ddc-5757 ext. 7234 headquarters, n.y., u.s.a. - tel: (631) 567-5600, fax: (631) 567-7358 southeast, u.s.a. - tel: (703) 450-7900, fax: (703) 450-6610 west coast, u.s.a. - tel: (714) 895-9777, fax: (714) 895-4988 united kingdom - tel: +44-(0)1635-811140, fax: +44-(0)1635-32264 ireland - tel: +353-21-341065, fax: +353-21-341568 france - tel: +33-(0)1-41-16-3424, fax: +33-(0)1-41-16-3425 germany - tel: +49-(0)8141-349-087, fax: +49-(0)8141-349-089 japan - tel: +81-(0)3-3814-7688, fax: +81-(0)3-3814-7689 world wide web - http://www.ddc-web.com the information in this data sheet is believed to be accurate; however, no responsibility is assumed by data device corporation for its use, and no license or rights are granted by implication or otherwise in connection therewith. specifications are subject to change without notice. http://www..net/ datasheet pdf - http://www..net/

▲Up To Search▲

Price & Availability of BU-61570

	To Download BU-61570 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .